Skip to content

Conversation

@samholmes
Copy link
Contributor

@samholmes samholmes commented Aug 15, 2025

CHANGELOG

Does this branch warrant an entry to the CHANGELOG?

  • Yes
  • No

Dependencies

none

Requirements

If you have made any visual changes to the GUI. Make sure you have:

  • Tested on iOS device
  • Tested on Android device
  • Tested on small-screen device (iPod Touch)
  • Tested on large-screen device (tablet)

cursor[bot]

This comment was marked as outdated.

@Jon-edge
Copy link
Collaborator

Jon-edge commented Sep 5, 2025

As with the other PRs, address non-deprecation warnings.
Really simple hands off task with gpt-5-fast in Cursor if claude+opencode is struggling for some reason on this.

displayCurrencyCode: selectedCryptoCurrencyCode,
exchangeAmount: isMaxAmount ? { max: true } : userInput,
fiatCurrencyCode: selectedFiatCurrencyCode,
amountType: lastUsedInput,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If lastUsedInput remains 'crypto' while cryptoInputDisabled becomes true (fiat-only plugins), the UI disables crypto input, but rampQuoteRequest still uses amountType: 'crypto'. That can trigger quote fetches with an unsupported amountType. Vice versa for fiat.

Suggestion: when computed disabled flags change, coerce lastUsedInput to a supported type (and optionally clear/convert userInput) so rampQuoteRequest always matches availability. Minimal guard alternative: do not build rampQuoteRequest if lastUsedInput corresponds to a disabled type.

disabled={cryptoInputDisabled}
/>
{/* MAX Button */}
<MaxButton active={isMaxAmount} onPress={handleMaxPress}>
Copy link
Collaborator

@Jon-edge Jon-edge Sep 8, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I recommend suggesting either guarding rampQuoteRequest when the selected
lastUsedInput is disabled, or auto-switching lastUsedInput to a supported type.

Or just disable this button when cryptoInputDisabled is true

This is an attempt to get the agent to automatically document lessons
learned to the docs/ directory. This way conventions are maintained and
over time as the agent is course corrected.
- Create docs/localization-guidelines.md with mandatory UI string localization rules
- Create docs/component-styling-guidelines.md with styled HOC usage patterns
- Update AGENTS.md with Documentation section indexing all docs/ files
- Add rule requiring all docs/ markdown files to be indexed in AGENTS.md
- Add localized strings for TradeRegionSelectScene to en_US.ts
This file contains run configuration such as RN_SIMULATOR and RN_PORT
to be used by a rn-ios script. This is for development purposes
This is a consistent card design for the new fiat buy UI.
- Implement TradeCreateScene and TradeOptionSelectScene for buy/sell flow
- Add Paybis as first ramp plugin with full API integration
- Create reusable hooks for ramp plugin management (useRampPlugins, useRampQuotes)
- Add payment type icon system with comprehensive mappings
- Implement quote fetching and comparison across multiple providers
- Add best rate badge component for quote comparison
- Create ramp plugin type definitions and store utilities
- Add comprehensive documentation for migration and architecture
- Include unit tests for payment types and store IDs
- Update navigation and deeplink handlers for ramp flows

BREAKING CHANGE: Replaces legacy FiatPluginUi with new ramp plugin system
Include plugin IDs in React Query key so quotes refetch when
region/currency/wallet changes affect available plugins. Simplify
queryFn to always check current plugins while reusing valid cached
quotes.
@samholmes samholmes force-pushed the sam/amount-type-filtering branch from 2e697a4 to c00b32f Compare September 10, 2025 04:27
cursor[bot]

This comment was marked as outdated.

@samholmes
Copy link
Contributor Author

Replaced by #5740

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants